Latest Variation
Original Post
I've even succeeded in confusing myself with the different variations I've been testing, so I've decided to start a new thread for this one. It combines ideas from several previously tested variations.
Perhaps my true calling in life was to be a whisky blender!
----------------------------------------------
Current rules for SF (see SuperFocus Rules link in top menu), except:
Column 2 must be cleared *before* starting on Column 1.
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2.
Unfinished tasks always go on the next page's C2.
Tasks in Column 2 can be deleted and entered on the next page without being worked on. This is the equivalent of putting the task on "snooze".
However if the next page is the last page, then these "snoozed" tasks are re-entered in Column 1 instead of Column 2.
----------------------------------
Back to the Poit Dhubh!
Perhaps my true calling in life was to be a whisky blender!
----------------------------------------------
Current rules for SF (see SuperFocus Rules link in top menu), except:
Column 2 must be cleared *before* starting on Column 1.
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2.
Unfinished tasks always go on the next page's C2.
Tasks in Column 2 can be deleted and entered on the next page without being worked on. This is the equivalent of putting the task on "snooze".
However if the next page is the last page, then these "snoozed" tasks are re-entered in Column 1 instead of Column 2.
----------------------------------
Back to the Poit Dhubh!
Reply by Mark Forster
A word or two on what I hope to achieve from this variation:
The original variation in which it was made compulsory to finish C2 before starting on C1 gave a very tight control and proved to be the most productive of all the variations I've tried. However it was rather a blunt instrument as far as timing was concerned and also the compulsory nature of the tasks started to raise resistance to the system after working with it for some time.
So to make it easier to adjust the timing I have blended it with the rule about where urgent tasks are entered, together with the "snooze" rule. The "snooze" rule also reduces the compulsory nature of the rules without - I hope - reducing their grip.
So essentially what is happening is that C1 and C2 form two separate lists which are worked on in turn. C1 tasks are only worked on if they are selected to be worked on, and C2 tasks are always worked on unless they are selected not to be worked on.
The original variation in which it was made compulsory to finish C2 before starting on C1 gave a very tight control and proved to be the most productive of all the variations I've tried. However it was rather a blunt instrument as far as timing was concerned and also the compulsory nature of the tasks started to raise resistance to the system after working with it for some time.
So to make it easier to adjust the timing I have blended it with the rule about where urgent tasks are entered, together with the "snooze" rule. The "snooze" rule also reduces the compulsory nature of the rules without - I hope - reducing their grip.
So essentially what is happening is that C1 and C2 form two separate lists which are worked on in turn. C1 tasks are only worked on if they are selected to be worked on, and C2 tasks are always worked on unless they are selected not to be worked on.
Reply by Erik
Nice blend!
Reply by sabre23t
I've been doing the C2 before C1 by sorting my Toodledo list with "Priority : Forwards", so my C2 task with priority "3 Top" is at the top of the list. I've effectively been "snoozing" my C2, just moving it forward one page "when I consider it done for now". I did find resistance to working on the list otherwise. I'm also keeping my C2 task not much more than one.
Hence, I'll follow the rules as you set out here. Particularly moving C2 to C1, if it was snoozed on the last page. I haven't done that so far.
Hence, I'll follow the rules as you set out here. Particularly moving C2 to C1, if it was snoozed on the last page. I haven't done that so far.
Reply by Tijl Kindt
I guess chronologically speaking it makes more sense now to put C1 on the right and C2 on the left side of the page? :P
Reply by Hugo Ferreira
> I guess chronologically speaking it makes more sense now
> to put C1 on the right and C2 on the left side of the page? :P
… which is exactly what I've been doing since Alan Baljeu's "Lefty Focus" thread ;)
http://www.markforster.net/forum/post/1409816
> to put C1 on the right and C2 on the left side of the page? :P
… which is exactly what I've been doing since Alan Baljeu's "Lefty Focus" thread ;)
http://www.markforster.net/forum/post/1409816
Reply by Alan Baljeu
Column 2 must be cleared *before* starting on Column 1. - YES!
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2. - COOL!
Unfinished tasks always go on the next page's C2. - Of Course!
Tasks in Column 2 can be deleted and entered on the next page without being worked on. This is the equivalent of putting the task on "snooze". - Handy!
However if the next page is the last page, then these "snoozed" tasks are re-entered in Column 1 instead of Column 2. - Sounds fair.
--------
Mark, you have NO idea how happy this version is for my work! This particular blend of rules happens to exactly fit the electronic system I've been following, but now I don't have to contort my operations to fit the rules :- the rules have contorted themselves to fit the system :-)
P.S. Poit Dhubh I've never heard of. Random guess - Port of Dublin?
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2. - COOL!
Unfinished tasks always go on the next page's C2. - Of Course!
Tasks in Column 2 can be deleted and entered on the next page without being worked on. This is the equivalent of putting the task on "snooze". - Handy!
However if the next page is the last page, then these "snoozed" tasks are re-entered in Column 1 instead of Column 2. - Sounds fair.
--------
Mark, you have NO idea how happy this version is for my work! This particular blend of rules happens to exactly fit the electronic system I've been following, but now I don't have to contort my operations to fit the rules :- the rules have contorted themselves to fit the system :-)
P.S. Poit Dhubh I've never heard of. Random guess - Port of Dublin?
Reply by Rainer
Poit Dhubh is a black pot whisky from the Isle of Skye (Scotland).
Reply by Erik
Alan
Might I ask what electronic solution you are using?
Might I ask what electronic solution you are using?
Reply by Greenchutney
Alan, I would like to know your electronic implementation as well.
GC
GC
Reply by 2mc
Mark,
Your method is *essentially* my latest Flagged Tasks with the exception of the new task that arises during the day and is urgent. (Which is easily handled in Flagged Tasks.)
I say "essentially* so as not to claim that it is exactly the same. There is only nuanced differences.
Matt
Your method is *essentially* my latest Flagged Tasks with the exception of the new task that arises during the day and is urgent. (Which is easily handled in Flagged Tasks.)
I say "essentially* so as not to claim that it is exactly the same. There is only nuanced differences.
Matt
Reply by Alan Baljeu
It's a little peculiar, but it works.
I'm using a MS OneNote notebook. Each section represents an SF column 1, but also has a count of completed tasks in column 2. One additional section labeled Active is divided into two: the column 2 for the active page, and the column 2 for the next page. As I advance pages in Column 1, I drag the Active page along as a bookmark, and up the column 2 counts.
I'm using a MS OneNote notebook. Each section represents an SF column 1, but also has a count of completed tasks in column 2. One additional section labeled Active is divided into two: the column 2 for the active page, and the column 2 for the next page. As I advance pages in Column 1, I drag the Active page along as a bookmark, and up the column 2 counts.
Reply by Sarah
I'm giving this a shot today, but I haven't had any C2s with more than one task yet today (I just finished my first pass through the list and have been carrying that one C2 task forward through little and often (grading a couple of student essays on each pass)) so I can't say yet how it's going to work for me. I like it in principle, though.
Reply by Mark Forster
Tijl:
<< I guess chronologically speaking it makes more sense now to put C1 on the right and C2 on the left side of the page? >>
I don't think it makes much difference - but I would point out that C1 gets written on first even though C2 gets actioned first. So I'll be keeping C1 on the left.
<< I guess chronologically speaking it makes more sense now to put C1 on the right and C2 on the left side of the page? >>
I don't think it makes much difference - but I would point out that C1 gets written on first even though C2 gets actioned first. So I'll be keeping C1 on the left.
Reply by Mark Forster
Rainer:
<< Poit Dhubh is a black pot whisky from the Isle of Skye (Scotland). >>
And significantly (for the analogy) it is not a single malt but a blended malt, and a very good one too.
<< Poit Dhubh is a black pot whisky from the Isle of Skye (Scotland). >>
And significantly (for the analogy) it is not a single malt but a blended malt, and a very good one too.
Reply by Mark Forster
2mc:
<< Your method is *essentially* my latest Flagged Tasks >>
I'm not sure where to find your latest Flagged Tasks. Is it the one at the "SF3 Alternative" thread? http://www.markforster.net/forum/post/1423027
I've just read through your rules there and can't really see the similarity. Yours seems to be based on flagging up tasks that need to be done today and doing all the work that needs doing on them before starting on non-flagged tasks. There's nothing resembling that in this variation.
<< Your method is *essentially* my latest Flagged Tasks >>
I'm not sure where to find your latest Flagged Tasks. Is it the one at the "SF3 Alternative" thread? http://www.markforster.net/forum/post/1423027
I've just read through your rules there and can't really see the similarity. Yours seems to be based on flagging up tasks that need to be done today and doing all the work that needs doing on them before starting on non-flagged tasks. There's nothing resembling that in this variation.
Reply by sabre23t
Alan Baljeu wrote about SF on MS OneNote ...
<< As I advance pages in Column 1, I drag the Active page along as a bookmark, and up the column 2 counts. >>
Does that mean you have a global column 2 counts (active page & next page)? On paper the column counts would be specific to each page.
In my SF on Toodledo, I'm not bothering tracking column 2 counts at all. I think the rule to take care of column 2 being full may just be an artifact of paper, rather than a critical SF feature. With this latest variation, when entering C2 on next page, you want it to be there and not the next next page, right?
<< As I advance pages in Column 1, I drag the Active page along as a bookmark, and up the column 2 counts. >>
Does that mean you have a global column 2 counts (active page & next page)? On paper the column counts would be specific to each page.
In my SF on Toodledo, I'm not bothering tracking column 2 counts at all. I think the rule to take care of column 2 being full may just be an artifact of paper, rather than a critical SF feature. With this latest variation, when entering C2 on next page, you want it to be there and not the next next page, right?
Reply by Alan Baljeu
"Does that mean you have a global column 2 counts (active page & next page)?"
no.
"the column counts would be specific to each page."
yes.
"I think the rule to take care of column 2 being full may just be an artifact of paper, rather than a critical SF feature."
That is certainly not Mark's opinion. Rather, the C2 count exists to ensure you don't abuse C2 and keep the list under control. The exact number of the limit could be adjusted though, and in my practise I rarely reach even 15.
no.
"the column counts would be specific to each page."
yes.
"I think the rule to take care of column 2 being full may just be an artifact of paper, rather than a critical SF feature."
That is certainly not Mark's opinion. Rather, the C2 count exists to ensure you don't abuse C2 and keep the list under control. The exact number of the limit could be adjusted though, and in my practise I rarely reach even 15.
Reply by sabre23t
<< the C2 count exists to ensure you don't abuse C2 and keep the list under control >>
Would limiting the C2 count to not more than say 5 active tasks be as effective? Tracking just active tasks instead of both done&active tasks is easier electronically, where you didn't duplicate/clone incomplete/recurring tasks, or maintain C2 done&active tasks counts per page.
Would limiting the C2 count to not more than say 5 active tasks be as effective? Tracking just active tasks instead of both done&active tasks is easier electronically, where you didn't duplicate/clone incomplete/recurring tasks, or maintain C2 done&active tasks counts per page.
Reply by Mark Forster
So far (Day 3) this variation is living up my hopes. But the problems with a variation usually only surface after a longer period than this, so it's too early to tell yet how effective it is.
Reply by Mark Forster
I've been finding that the rule that "snoozed" tasks can only be entered in C1 on the last page is getting in the way rather than helping. In it's place I'm experimenting with a rule that any C2 task can be returned to C1 at any time.
So the rules for this variation are now:
----------------------------------------------
Current rules for SF (see SuperFocus Rules link in top menu), except:
Column 2 must be cleared *before* starting on Column 1.
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2.
Unfinished tasks always go on the next page's C2.
Tasks in C2 may be deleted and re-entered in C2 of the next page without being worked on. This is the equivalent of putting the task on "snooze".
Tasks in Column 2 may be deleted and entered in Column 1 of the last page without being worked on. This demotes the task back to normal priority.
----------------------------------
So the rules for this variation are now:
----------------------------------------------
Current rules for SF (see SuperFocus Rules link in top menu), except:
Column 2 must be cleared *before* starting on Column 1.
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2.
Unfinished tasks always go on the next page's C2.
Tasks in C2 may be deleted and re-entered in C2 of the next page without being worked on. This is the equivalent of putting the task on "snooze".
Tasks in Column 2 may be deleted and entered in Column 1 of the last page without being worked on. This demotes the task back to normal priority.
----------------------------------
Reply by Seraphim
Mark,
This is looking very similar to what I've actually been doing for a few weeks. Not exactly the same, but very close:
<< Column 2 must be cleared *before* starting on Column 1. >>
I've been using this rule for a few weeks now, and really like it. It makes things move along faster.
<< Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2. >>
My rule generally gives the same effect, but it's based on my level of anxiety: First consider putting the urgent task in C2 on next page, but if that makes me anxious, then put it in C2 of the current page. Generally it makes me anxious if I'm still working on C2 of the current page (thus, getting to the next page is relatively distant). So it produces the same effect, but using a different rule.
<< Unfinished tasks always go on the next page's C2. >>
I am also using this rule.
<< Tasks in C2 may be deleted and re-entered in C2 of the next page without being worked on. This is the equivalent of putting the task on "snooze". >>
I also do this, but generally I want to have a REASON -- e.g., I cannot physically do the task now; or it's a sizable personal task and I'm on working time, or vice-versa. Sometimes I'll do this if I have a hard time limit and I can't fit the task (even using "little and often") into the time that I have.
I want a REASON, for fear that I will abuse C2 and start copying things forward all the time for no good reason. But maybe the repeated rewriting will eventually convince you to take action (or demote back to C1).
I wonder if this rule would have the same effect for people using a software-based approach to SF. They wouldn't get the "benefit" of repeated rewriting.
<< Tasks in Column 2 may be deleted and entered in Column 1 of the last page without being worked on. This demotes the task back to normal priority. >>
I have been doing this for a while, too, generally when priorities have changed and something really doesn't deserve the attention of a C2 task.
This is looking very similar to what I've actually been doing for a few weeks. Not exactly the same, but very close:
<< Column 2 must be cleared *before* starting on Column 1. >>
I've been using this rule for a few weeks now, and really like it. It makes things move along faster.
<< Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2. >>
My rule generally gives the same effect, but it's based on my level of anxiety: First consider putting the urgent task in C2 on next page, but if that makes me anxious, then put it in C2 of the current page. Generally it makes me anxious if I'm still working on C2 of the current page (thus, getting to the next page is relatively distant). So it produces the same effect, but using a different rule.
<< Unfinished tasks always go on the next page's C2. >>
I am also using this rule.
<< Tasks in C2 may be deleted and re-entered in C2 of the next page without being worked on. This is the equivalent of putting the task on "snooze". >>
I also do this, but generally I want to have a REASON -- e.g., I cannot physically do the task now; or it's a sizable personal task and I'm on working time, or vice-versa. Sometimes I'll do this if I have a hard time limit and I can't fit the task (even using "little and often") into the time that I have.
I want a REASON, for fear that I will abuse C2 and start copying things forward all the time for no good reason. But maybe the repeated rewriting will eventually convince you to take action (or demote back to C1).
I wonder if this rule would have the same effect for people using a software-based approach to SF. They wouldn't get the "benefit" of repeated rewriting.
<< Tasks in Column 2 may be deleted and entered in Column 1 of the last page without being worked on. This demotes the task back to normal priority. >>
I have been doing this for a while, too, generally when priorities have changed and something really doesn't deserve the attention of a C2 task.
Reply by Seraphim
Mark,
How do you think your original experiment would have fared with this variation (War and Peace with no backlogs)?
How do you think your original experiment would have fared with this variation (War and Peace with no backlogs)?
Reply by Mark Forster
Seraphim:
<< I also do this, but generally I want to have a REASON -- e.g., I cannot physically do the task now; or it's a sizable personal task and I'm on working time, or vice-versa. >>
I agree. I always have a similar reason to yours. It's not intended to be a way of avoiding doing something. Bear in mind that the tasks are only there because they are urgent or because you have already done some work on them - so they already have some impetus behind them.
<< I also do this, but generally I want to have a REASON -- e.g., I cannot physically do the task now; or it's a sizable personal task and I'm on working time, or vice-versa. >>
I agree. I always have a similar reason to yours. It's not intended to be a way of avoiding doing something. Bear in mind that the tasks are only there because they are urgent or because you have already done some work on them - so they already have some impetus behind them.
Reply by Mark Forster
Seraphim:
<< How do you think your original experiment would have fared with this variation (War and Peace with no backlogs)? >>
That's easily answered. I have no backlogs, and I keep one book in Column 2 which is coming along just fine.
<< How do you think your original experiment would have fared with this variation (War and Peace with no backlogs)? >>
That's easily answered. I have no backlogs, and I keep one book in Column 2 which is coming along just fine.
Reply by Mark Forster
I'm still not quite satisfied with the rules for C2, so I am going to experiment with "demoting" unactioned tasks from C2 back to C1.
So the rules I am working on now are:
----------------------------------------------
Current rules for SF (see SuperFocus Rules link in top menu), except:
Column 2 must be cleared *before* starting on Column 1. If any tasks in C2 are left unactioned they are re-entered on the last page in C1.
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2.
Unfinished tasks always go on the next page's C2.
----------------------------------
So the rules I am working on now are:
----------------------------------------------
Current rules for SF (see SuperFocus Rules link in top menu), except:
Column 2 must be cleared *before* starting on Column 1. If any tasks in C2 are left unactioned they are re-entered on the last page in C1.
Urgent tasks are entered on the current page's C2 until you've started on C1. Once you've started on C1, then urgent tasks go on the next page's C2.
Unfinished tasks always go on the next page's C2.
----------------------------------
Reply by FocusGuy.
If any tasks in C2 are left unactioned they are re-entered on the last page in C1
This is exactly what i do from the beginning of sf just because i noticed that there was some urgent task i was unable to do. I was just un able to do it and even wondered if i had to do it or not. Finaly i reinterd them on the last page at c1 and all began suddently perfectly clear.
I also want to add that superfocus works perfectly on a digital page such as .page with two colums and it even easier that on a papernotebook for me.
This is exactly what i do from the beginning of sf just because i noticed that there was some urgent task i was unable to do. I was just un able to do it and even wondered if i had to do it or not. Finaly i reinterd them on the last page at c1 and all began suddently perfectly clear.
I also want to add that superfocus works perfectly on a digital page such as .page with two colums and it even easier that on a papernotebook for me.
Reply by Bernie
Mark, I am missing the distinction between the current variation that you described just above on Apr 19, vs. the one you described Apr. 14. In both cases, the feature under test is that C2 tasks can be demoted to C1 at any time. Are there differences in the other details?
I am watching these experiments with great interest, as I have that "almost perfect" feeling about SF. As you put it earlier, there is a certain timing issue once tasks get into C2. There are times when I want to be in-progress on, say tasks X, Y, and Z, but I cannot or do not want to work on them in a strict rotation. Rather, XYXZZXYYXZ or any such variation (working on little C1 items in between each capital letter). Maybe it feels good to get started on Y in a smallish way in the morning, but the intense work will fit much better in the afternoon.
There are various ways to achieve this pattern using an external project list and adjusting the notion of "done" to allow these tasks to come and go from C2 at will, but it would be really excellent if some C2 rule adjustment would allow this to happen without the external list and without opening too many loopholes.
A tall order, but if anyone can figure it out, it's you! Thanks for continually innovating and testing.
I am watching these experiments with great interest, as I have that "almost perfect" feeling about SF. As you put it earlier, there is a certain timing issue once tasks get into C2. There are times when I want to be in-progress on, say tasks X, Y, and Z, but I cannot or do not want to work on them in a strict rotation. Rather, XYXZZXYYXZ or any such variation (working on little C1 items in between each capital letter). Maybe it feels good to get started on Y in a smallish way in the morning, but the intense work will fit much better in the afternoon.
There are various ways to achieve this pattern using an external project list and adjusting the notion of "done" to allow these tasks to come and go from C2 at will, but it would be really excellent if some C2 rule adjustment would allow this to happen without the external list and without opening too many loopholes.
A tall order, but if anyone can figure it out, it's you! Thanks for continually innovating and testing.
Reply by Mark Forster
Bernie:
<< I am missing the distinction between the current variation that you described just above on Apr 19, vs. the one you described Apr. 14. In both cases, the feature under test is that C2 tasks can be demoted to C1 at any time. Are there differences in the other details? >>
There are two differences, one quite major and the other relatively minor.
1) The ability to put a C2 task "on snooze" has been removed. All tasks in C2 which are not worked on are "demoted" to C1. I was finding that the "snooze" rule resulted in a collection of tasks which travelled along with me in C2 without getting actioned. This removed a lot of the purpose of C2 and also increased my resistance to working on the list. Now the choice is simple: Work on it or it will be put back in C1.
2) The second change is more subtle. In the April 14 rules the decision to "snooze" a task or move it to C1 was a positive one. This meant that when you considered a C2 task, you had four choices: i) do some work on it, ii) put it on snooze; iii) move it to C1; iv) leave it for now. This was getting a long way from the simple concept of "do it if it stands out". The April 19 rules restore "Do it if it stands out" as the only option. Any C2 tasks which don't stand out are moved to C1 automatically. Although this may seem to be quite a minor change, it makes working the list more intuitive, which was beginning to get lost.
<< I am missing the distinction between the current variation that you described just above on Apr 19, vs. the one you described Apr. 14. In both cases, the feature under test is that C2 tasks can be demoted to C1 at any time. Are there differences in the other details? >>
There are two differences, one quite major and the other relatively minor.
1) The ability to put a C2 task "on snooze" has been removed. All tasks in C2 which are not worked on are "demoted" to C1. I was finding that the "snooze" rule resulted in a collection of tasks which travelled along with me in C2 without getting actioned. This removed a lot of the purpose of C2 and also increased my resistance to working on the list. Now the choice is simple: Work on it or it will be put back in C1.
2) The second change is more subtle. In the April 14 rules the decision to "snooze" a task or move it to C1 was a positive one. This meant that when you considered a C2 task, you had four choices: i) do some work on it, ii) put it on snooze; iii) move it to C1; iv) leave it for now. This was getting a long way from the simple concept of "do it if it stands out". The April 19 rules restore "Do it if it stands out" as the only option. Any C2 tasks which don't stand out are moved to C1 automatically. Although this may seem to be quite a minor change, it makes working the list more intuitive, which was beginning to get lost.
Reply by malisa
I haven't tried it yet, but I like this variation philosophically over the previous one for the reasons Mark sited in #2 above. I felt like there were too many ways to make excuses. But I also found with shifting priorities, I often wanted to demote items to C1 from C2, and did. So I guess I've been doing this variation intermittently. It seems to be the most common sense variation to me.
Reply by Jeff N
<>
Doesn't this variation dilute the emphasis on COMPLETING tasks quite a bit? I had understood that to be a major aspect/benefit of SuperFocus, as compared to earlier AF.
Doesn't this variation dilute the emphasis on COMPLETING tasks quite a bit? I had understood that to be a major aspect/benefit of SuperFocus, as compared to earlier AF.
Reply by Mark Forster
JeffN:
Well, that's one of the things I hope to find out by testing it!
Well, that's one of the things I hope to find out by testing it!
Reply by Bernie
<< There are two differences, one quite major and the other relatively minor. ... >>
Thank you, Mark. Upon rereading, it seems crystal clear now. I must have been up past my bedtime!
Thank you, Mark. Upon rereading, it seems crystal clear now. I must have been up past my bedtime!
Reply by Mark Forster
Bernie:
Don't worry. I get confused myself!
Don't worry. I get confused myself!
Reply by ubi
I like the snooze feature and the demotion to C1 whenever a C2 task is continued or snoozed all the way to the end of the list.
But I have an issue with the strict all-C2-before-C1 rule: If I've just continued a C1 task to C2 on the next page (with no other unactioned C2 tasks listed), and nothing else stands out on the current page, it seems I am forced to immediately continue, snooze, or demote the same task. In this case, I cannot choose a C1 task on the new current page, as a way to alternate my work before reconsidering the same task I had just actioned. For this reason, and since I make rare use of C2 anyway, I'm not adopting this C2-before-C1 variation.
But I have an issue with the strict all-C2-before-C1 rule: If I've just continued a C1 task to C2 on the next page (with no other unactioned C2 tasks listed), and nothing else stands out on the current page, it seems I am forced to immediately continue, snooze, or demote the same task. In this case, I cannot choose a C1 task on the new current page, as a way to alternate my work before reconsidering the same task I had just actioned. For this reason, and since I make rare use of C2 anyway, I'm not adopting this C2-before-C1 variation.
Reply by Sabrina
Personally my favourite variation thus far has been this one because of its simplicity:
<< What this means is basically AF1 with a second column added in which urgent tasks go on the page I am currently working on and unfinished tasks on the next page. The dismissal rules are exactly the same as for AF1 with Column 2 treated as part of the page. >>
AF1 has always flowed very naturally for me, and with the added Column 2 it gave just the right amount of flexibility.
<< What this means is basically AF1 with a second column added in which urgent tasks go on the page I am currently working on and unfinished tasks on the next page. The dismissal rules are exactly the same as for AF1 with Column 2 treated as part of the page. >>
AF1 has always flowed very naturally for me, and with the added Column 2 it gave just the right amount of flexibility.
Reply by Mark Forster
ubi:
These are only experiments which I am carrying out myself. Other people are welcome to try them too but the "official" rules for SuperFocus remain the "SuperFocus Rules" accessed through the top menu.
These are only experiments which I am carrying out myself. Other people are welcome to try them too but the "official" rules for SuperFocus remain the "SuperFocus Rules" accessed through the top menu.
Reply by Bernie
<<<< What this means is basically AF1 with a second column added in which urgent tasks go on the page I am currently working on and unfinished tasks on the next page. The dismissal rules are exactly the same as for AF1 with Column 2 treated as part of the page. >>>>
Sabrina, is that the variation in which we discussed "parking" unfinished tasks in C2? That may be my favorite as well, though I didn't stay on that variation for very long, as I've been following along with most of Mark's experiments.
I saw it as letting unfinished tasks have a continuum of priorities, from "work on this every page turn," to "work on it a couple of page turns per list cycle." The remnants left in C2 showed me at a glance which projects were in-progress, vs. those in C1 which I hadn't started yet. I remember feeling motivated to follow up on C2 items, without the resistance caused by the standard version's forced march.
Sabrina, is that the variation in which we discussed "parking" unfinished tasks in C2? That may be my favorite as well, though I didn't stay on that variation for very long, as I've been following along with most of Mark's experiments.
I saw it as letting unfinished tasks have a continuum of priorities, from "work on this every page turn," to "work on it a couple of page turns per list cycle." The remnants left in C2 showed me at a glance which projects were in-progress, vs. those in C1 which I hadn't started yet. I remember feeling motivated to follow up on C2 items, without the resistance caused by the standard version's forced march.
Reply by Mark Forster
Bernie:
It's this one:
http://www.markforster.net/forum/post/1453964
I can't actually remember why it was that I moved on from there. Maybe I just got another bright idea and wanted to see how it would work.
So I might go back and have another shot at it.
It's this one:
http://www.markforster.net/forum/post/1453964
I can't actually remember why it was that I moved on from there. Maybe I just got another bright idea and wanted to see how it would work.
So I might go back and have another shot at it.